MINOR: fix security_test for ZK case due to error change#10225
MINOR: fix security_test for ZK case due to error change#10225rondagostino wants to merge 1 commit into
Conversation
|
@abbccdda, @cmccabe. Ported from #10199 to discuss separately. We used to see this error message in The test does a Now we are instead seeing this in the log file: And of course now the test fails. The It is a simple matter to make the test pass -- I have confirmed that it passes if we I think we just need to decide if this change in behavior is acceptable or not. |
|
@rondagostino Thanks for identifying the issue. Returning |
|
This PR "fixes" the issue by changing the system test to check for the new error. We can close this PR in favor of another one if @abbccdda decides the behavior change is incorrect and can be corrected. |
|
Closed in favor of #10240 |
2 participants
The ZooKeeper version of this system test is failing because the producer is no longer seeing
LEADER_NOT_AVAILABLE. When the broker sees a METADATA request for the test topic after it restarts the auto topic creation manager is determining that the topic needs to be created due to the TLS hostname verification failure on the inter-broker security protocol. It also thinks there aren't enough brokers available to meet the default topic replication factor (it sees 0 available due to the TLS issue), so it returnsINVALID_REPLICATION_FACTORfor that topic in the Metadata response. In other words, the flow has changed and the inability to produce is not manifesting as it was before, and the test is failing. This patch updates the test to check forINVALID_REPLICATION_FACTORinstead ofLEADER_NOT_AVAILABLE.Committer Checklist (excluded from commit message)